A security flaw was found in the way the Sleuth Kit (TSK), a collection of UNIX-based command line tools allowing to investigate a computer, performed management of '.' (dotfile) file system entry. An attacker could use this flaw to evade detection by forensic analysis (hide certain files not to be scanned) by renaming the file in question it to be '.' file system entry.

The original reports speaks about this attack vector to be present when scanning FAT (File Allocation Table) file system. It is possible though, the flaw to be present on other file systems, which do not reserve usage of '.' entry for special purpose, too.

References: [1] http://www.openwall.com/lists/oss-security/2012/12/01/2 [2] http://sourceforge.net/mailarchive/forum.php?threadname=1305739444.2355.35.camel%40zwerfkat&forumname=sleuthkit-users [3] http://sourceforge.net/mailarchive/forum.php?threadname=20120503111900.GL18142%40hauptmenue&forumname=sleuthkit-users [4] http://labs.bitdefender.com/2012/06/flame-the-story-of-leaked-data-carried-by-human-vector/ [5] http://blog.crysys.hu/2012/06/flame-usb-dot-file-confirmed/ [6] http://www.openwall.com/lists/oss-security/2012/12/04/2

Upstream bug report: [7] http://sourceforge.net/tracker/?func=detail&aid=3523019&groupid=55685&atid=477889

Upstream patch: OSS-security post [1] mentions no upstream patch to correct this issue to be available yet / so far.

Integer overflow in the "file" program 4.20, when running on 32-bit systems, as used in products including The Sleuth Kit, might allow user-assisted attackers to execute arbitrary code via a large file that triggers an overflow that bypasses an assert() statement. NOTE: this issue is due to an incorrect patch for CVE-2007-1536.